home *** CD-ROM | disk | FTP | other *** search
-
- john@bunny.four.net (John Wallace Williams) writes:
-
- >>I have many copies of PC-NFS v4.0 and would like to use WinSock
- >>applications. Unfortunately, I cannot upgrade to v5.0 just now. So, is
- >>there a version of WinSock that I could use if I switch to the NDIS
- >>drivers that come with PC-NFS?
-
- >>Thanks for any suggestions,
-
- >>Randy Moore
-
-
- >I'm running PC-NFS 3.5c and I would like to do the same. I've managed
- >to get NFS and WINSOCK applications running concurrently using the PKTMUX
- >program to handle two packet drivers, one for each.
- >( obtain pktmux12.exe , pktd.sys & wintcpa1.zip from ftp )
-
- >When I try to use NDIS to handle the ethernet card, I have problems.
- >I've used it with lanman 1.1 & 2.1, the newest NFS-NDIS.SYS (from york.ac.uk)
- >and DIS_PKT.SYS (v 1.05, 1.09 & 1.11).
-
- >PC-NFS currently runs fine over NDIS. The packet driver (for winsock) works,
- >but only when I dont do nfsrun! I cant get both to work simultaneously. :/
- >Am I missing something? Does NDIS handle dual clients like I think it does?
-
- >-- My protocol.ini --
- >[NFS-NDIS]
- > drivername = NFSLINK$
- > bindings = SMCMAC
-
- >[PKTDRV]
- > drivername = PKTDRV$
- > bindings = SMCMAC
- > intvec = 0x60
- > chainvec = 0x66
-
- >[SMCMAC]
- > drivername = SMCMAC$
- > ramaddress = 0xD800
- > iobase = 0x280
- > irq = 3
- >; receivebufsize = 1536
-
- >[protocol manager]
- > drivername = PROTMAN$
- >--
-
- >I've spent all weekend rebooting the machine with different configurations,
- >but to no avail. PKTMUX does the job tho. Performance and memory take a hit,
- >thats why i'd rather use NDIS to solve the problem.
-
- >Anyone out there currently doing this? I'm more of a UNIX type, so please
- >dont flame me if i'm doing something obviously wrong :)
-
- >Thanks in advance!
-
-
- I have had the same problem using the NDIS drivers for PC-NFS 4.0a. I
- was unable to find a solution using NFS-NDIS.SYS 4.0a.
-
- My solution is to use the 1) NDIS MAC driver, 2) two copies of DIS_PKT,
- and 3) the packet driver interface for PC-NFS. This allowed me to achieve
- my goal of mounting Unix disks and also being able to use winsock
- applications.
-
- The PC-NFS 4.0a packet driver interface, PKTD.SYS 4.0.a3 can be found at
- ftp.york.ac.uk or at ftp.sunet.se (/pub/pc/pc-nfs/mirror-york).
-
- DISPKT11.ZIP can be found at casbah.acns.nwu.edu /pub/nupop/ndis_pkt.
- I hacked one copy of DIS_PKT.DOS and changed all (3 total) references to
- PKTDRV to PKTDR1, naming the result DIS_PK1.DOS. A similar result could
- be obtained by modifying DIS_PKT.ASM, compiling, linking and EXE2BINing.
-
-
- SCHEMATIC:
- SMC8000.DOS
- (NDIS MAC driver)
- |
- ------------------------------------------------
- | |
- DIS_PKT.DOS DIS_PK1.DOS
- (packet driver shim) (modified packet driver shim) | |
- | |
- WINPKT.COM PKTD.SYS
- (Windows virtual packet driver (packet driver interface
- for Trumpet WinSock alpha #18) for PC-NFS 4.0a )
- | |
- Trumpet WinSock alpha #18 PC-NFS 4.0a
-
-
- CONFIG.SYS:
-
- devicehigh=c:\boot\pcnfs.sys
- devicehigh=c:\boot\sockdrv.sys
- devicehigh=c:\lanman\pktd.sys
- DEVICE=c:\lanman\protman.sys
- DEVICEhigh=C:\LANMAN\SMC8000.DOS
- DEVICEhigh=C:\LANMAN\dis_pk1.dos
- DEVICEhigh=C:\LANMAN\dis_pkt.dos
-
-
- PROTOCOL.INI:
-
- [protocol manager]
- drivername=protman$
-
- [smc]
- drivername=smc8000$
-
- [pktdr2]
- drivername=pktdr2$
- bindings=smc
- intvec=0x62
-
- [pktdr1]
- drivername=pktdr1$
- bindings=smc
- intvec=0x61
-
- [pktdrv]
- drivername=pktdrv$
- bindings=smc
- intvec=0x60
-
-
- AUTOEXEC.BAT
-
- c:\lanman\netbind
- set tz=CST
- set nfsdrive=D
- set nfspath=D:\NFS
- lh prt *
- net init
- rtm
- winpkt 0x60
- win.com
-
-
- This is what works for me. Good Luck.
- From news@bigblue.oit.unc.edu Fri Feb 18 21:50:45 1994
- Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
- id AA25589; Fri, 18 Feb 1994 17:27:11 -0500
- Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
- id AA11798; Fri, 18 Feb 1994 17:22:17 -0500
- Received: from GATEWAY by bigblue with netnews
- for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
- To: winsock@sunsite.unc.edu
- Date: 18 Feb 1994 21:50:45 GMT
- From: keele@herald.usask.ca (A. Ross Keele)
- Message-Id: <2k3d7l$72f@tribune.usask.ca>
- Organization: University of Saskatchewan
- Sender: ses
- Subject: Re: COMM driver for Windows ?
-
- In article <CLEsDH.Kqu@autelca.ascom.ch> nbladt@autelca.ascom.ch
- (Norbert Bladt) writes:
-
- >Why don't you (and Karl) don't use the wfxcomm.drv freely available and
- >written by Delrina (WinFax 3.0). It worked for me, it's faster than
- >the comm.drv and it supports the 16550 UART !
-
- >Norbert.
-
- >Sorry, I don't know where to get it. It might be on Compu$erve or other BBS'es
- >around the world. Sometime ago it was posted in a newsgroup related to
- >ms-windows. If really nobody is able to dig it up, I can post it
- >here if it's not too big (I can't remember how big it really is).
- >I know this is not a binary group, etc. pp. But this exception to the rule
- >might be OK (depending on the size, of course).
-
- You can get it at a number of places. A fast connectin is with ftp.halcyon.com
- in the /pub/supra directory. The file is wfxcomm.zip.
- --
- A. Ross Keele Keele@Herald.Usask.CA
- Cognitive Science Lab Keele@Sask.Usask.CA
- Dept. of Psychology (306)966-6696
- University of Saskatchewan Saskatoon, SK CANADA S7N 0W0
- From news@bigblue.oit.unc.edu Fri Feb 18 22:39:37 1994
- Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
- id AA04711; Fri, 18 Feb 1994 18:27:10 -0500
- Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
- id AA13408; Fri, 18 Feb 1994 18:17:03 -0500
- Received: from GATEWAY by bigblue with netnews
- for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
- To: winsock@sunsite.unc.edu
- Date: 18 Feb 1994 22:39:37 GMT
- From: smd@hrt213.brooks.af.mil (Sten Drescher)
- Message-Id: <SMD.94Feb18163937@hrt213.brooks.af.mil>
- Organization: Intelligent Training Branch, Brooks AFB
- Sender: ses
- References: <1994Feb17.063544.12724@dcc.uchile.cl>, <Zorc.93.2D647997@olimp.irb.hr>
- Subject: Re: IRC for Winsock?
-
- On Fri, 18 Feb 1994 08:17:27 GMT, Zorc@olimp.irb.hr (Hrvoje Zorc) said:
-
- Hrvoje> In article <1994Feb17.063544.12724@dcc.uchile.cl> ereimber@dcc.uchile.cl (Erich Reimberg N.) writes:
- >> From: ereimber@dcc.uchile.cl (Erich Reimberg N.)
- >> Is there any IRC client application for using with Winsock ?
-
- Hrvoje> Yes, it is called wirc101.zip and you can find it at
- Hrvoje> petros.psychol.utas.edu.au /pub.
- Are you sure that's where you got it? I just looked, and
- couldn't find it.
- --
- Sten Drescher smd@floyd.brooks.af.mil
- #include <disclaimer.h>
- All my activities have been purely intellectual, solely intellectual.
- -Peter Melzer, physics teacher at the Bronx High School of
- Science and longtime leader of the North American Man/Boy Love
- Association [Knight-Ridder Newspapers]
- From news@bigblue.oit.unc.edu Fri Feb 18 23:28:02 1994
- Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
- id AA12288; Fri, 18 Feb 1994 19:27:10 -0500
- Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
- id AA09878; Fri, 18 Feb 1994 19:02:49 -0500
- Received: from GATEWAY by bigblue with netnews
- for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
- To: winsock@sunsite.unc.edu
- Date: 18 Feb 1994 23:28:02 GMT
- From: Kwillis@ccwf.cc.utexas.edu (Keith Willis)
- Message-Id: <2k3iu2$a86@geraldo.cc.utexas.edu>
- Organization: University of Texas at Austin
- Sender: ses
- Subject: Winsock 1.0a - Can a hostname be assigned to slip?
-
- I have a question for anyone out there who may know. I use winsock 1.0a
- with a slip connection through the University. Every time I dial in, I get a new IP
- address and access it using Bootp. It would be nice to be able to assign a name to my
- computer so that if someone wishes to talk to me or access my terminal in general, they
- can access the 'name' and then it could be resolved into the IP address. It seems
- extremely feasible and sensible. Does anyone know if it can be done and if so, how to
- do it? Any help is much appreciated. Even how this might be done were I to do it myself.
- Thanks in advance,
- Keith W.
- From fit106@its.csiro.au Sat Feb 19 23:50:15 1994
- Received: from commsun.its.csiro.au by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
- id AA22495; Fri, 18 Feb 1994 20:51:28 -0500
- Received: by commsun.its.CSIRO.AU id AA26678
- (5.65c/IDA-1.4.4 for winsock@sunsite.unc.edu); Sat, 19 Feb 1994 12:50:36 +1100
- Date: Sat, 19 Feb 1994 12:50:15 +1100 (EST)
- From: Kent Fitch <Kent.Fitch@its.csiro.au>
- Subject: WinQVT/Net 3.96, dated 30jan94 run time err 202
- To: winsock@sunsite.unc.edu
- Message-Id: <Pine.3.07.9402191213.C25527-a100000@commsun.its.CSIRO.AU>
- Mime-Version: 1.0
- Content-Type: TEXT/PLAIN; charset=US-ASCII
-
- Has anyone else had this error? I have reported it to QPC, but someone
- else may have solved it:
-
- we are trying out the latest WinQVT/Net 3.96 (I think .5) dated 30jan94.
- Occassionally, whilst scrolling fast within a telnet window (eg, down
- arrow key held down in the PINE mail reader, or in "vi"), we have been
- getting a error message box popping up saying:
-
- "Run time error 202
- at 000D:0164"
-
- Another user got the same error, also doing scrolling, at location "000C:016C"
-
- Similar problems had been reported to us with 3.94 (ie, WinQVT/Net hanging
- whilst scrolling), but I had never experienced this myself.
-
- We are mostly using TRUMPET WINSOCK Alpha #16, #18, and the release 1.0 -
- it seems to happen with all.
-
- The work around seems to be "dont scroll too fast" - any ideas?
-
- Kent Fitch Ph: +61 6 276 6711
- ITSB CSIRO Canberra Australia kent.fitch@its.csiro.au
- "The mass of men lead lives of quiet desparation" - HD Thoreau
-
-
-
-
-